SCS provides a very basic REST API for users to call remotely via their own applications. You can access this API via HTTP GET calls to the primary SCS web server with the /SVC route.
If you have a need or suggestion to improve this functionality for your usage please reach out. As this is a more advanced feature of SCS we have not built out to robust an interface as we are not as cognizant of the user-bases requirements so we're very willing to tailor it once we know what exactly you need.
By default all methods below are HTTP GET, any deviation will be otherwise noted for the given endpoint.
[SCS HOST]/svc/GetCurrentDeviceConfiguration
Returns the current device configuration XML for the ship
[SCS HOST]/svc/GetDeviceConfiguration/{xmlReleaseID}
Returns a specific device configuration XML for the ship based upon the passed xmlReleaseID parameter
[SCS HOST]/svc/GetMessageDefinitionForDataField/{xmlReleaseID}/{datafieldID}
Returns the configuration XML for a single Message Definition which contains a specific datafield.
xmlReleaseID parameter will specific which Device Configuration to search
datafieldID parameter will search the Device Configuration for the single specific Data Field who's parent Message Definition will be returned.
[SCS HOST]/svc/GetAcqLoggingStatus
Returns JSON informing caller whether or not ACQ is currently logging or not.
This does NOT indicate if ACQ service itself is running or not. ACQ may be actively sending out data to clients even if it is not logging that data to disk!
JSON will have a success boolean, a state string and optionally an errorMsg string if an error is encountered.

[SCS HOST]/svc/IsRunningLatestVersionOfSCS
Returns a JSON result informing caller if local ship installation of SCS matches what is currently available from shore.
JSON will have a single isUpToDate boolean.

[SCS HOST]/svc/GetEventData/{eventIdStr}/{format?}
Returns data collected by an SCS Event in the requested format.
The eventIdStr parameter can be obtained by the event itself. The conceptualized flow here is that the event calls your code via an Execute Web Hook action sequence (which provides your code with the eventID string used here) when appropriate (such as when the event ends so you can automatically and instantly download the event data).
eventIdStr parameter is the ID of the event run you wish to query for data
format parameter is optional, default value is "xml". Valid values are "xml" or "legacy"
SCSv5 Page 1 of 1